thanks @benediktibk to add this for the stm32F7.

Recently there was a similar question for the stm32h7 serie here #76297
Does it make sense to extend this PR to the stm32H7 serie ?
The stm32H7 flash registers do not have exactly the same mapping as the stm32F7. In any case that could be a next PR to come just after that one is merged.

LGTM
did you run any test with CONFIG_FLASH_STM32_READOUT_PROTECTION set ?
(of course changing the RDP might be ... definitive, to be handled with care or simulated)

Yes, I ran tests with changes between RDP level 0 and 1, none with 2. For obvious reasons.

thanks @benediktibk to add this for the stm32F7.

Recently there was a similar question for the stm32h7 serie here #76297
Does it make sense to extend this PR to the stm32H7 serie ?
The stm32H7 flash registers do not have exactly the same mapping as the stm32F7. In any case that could be a next PR to come just after that one is merged.

I'll look into it, but I won't be able to test it on hardware.

thanks @benediktibk to add this for the stm32F7.
Recently there was a similar question for the stm32h7 serie here #76297
Does it make sense to extend this PR to the stm32H7 serie ?
The stm32H7 flash registers do not have exactly the same mapping as the stm32F7. In any case that could be a next PR to come just after that one is merged.

I'll look into it, but I won't be able to test it on hardware.

Thanks for adding this serie.

thanks @benediktibk to add this for the stm32F7.
Recently there was a similar question for the stm32h7 serie here #76297
Does it make sense to extend this PR to the stm32H7 serie ?
The stm32H7 flash registers do not have exactly the same mapping as the stm32F7. In any case that could be a next PR to come just after that one is merged.

I'll look into it, but I won't be able to test it on hardware.

I have tested on stm32h750b_dk board
I am afraid this is not as simple as I expected. I realize, the flash driver for stm32h7 is apart from other stm32 series. It does not include (build) the flash_stm32_ex_op.c nor flash_stm32.c (see drivers/flash/CMakeLists.txt)
Consequently the stm32h7_flash driver probably needs more than
the api function .ex_op = flash_stm32_ex_op, or .ex_op = flash_stm32h7_ex_op but also either re-defining the flash_stm32_ex_op.c or a new flash_stm32h7_ex_op.c. This has to be studied further.
Sorry for that, maybe in the end we better have a dedicated PR if that one is going too far in changes for stm32H7

I took your commit f2fe52c7d04f7d8682c2067887fc32b17f46fe4f and applied the model to the stm32h7 : this gives #76640

Thanks @FRASTM, I've removed the two commits for the H7 from this PR again.